X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C81BF2.C3FDCBBE@onstor-exch02.onstor.net>; Wed, 31 Oct 2007 12:18:06 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C81BF2.C3FDCBBE"
Content-class: urn:content-classes:message
Subject: RE: Hostnames, Filer Names, and Cluster Names... Case Sensitive or Not?
Date: Wed, 31 Oct 2007 12:18:05 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E0648DE70@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E03E9A407@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Hostnames, Filer Names, and Cluster Names... Case Sensitive or Not?
Thread-Index: Acgb7xtGuD+p+nu/Rs2bAITEGwg77QAA4PlQ
References: <BB375AF679D4A34E9CA8DFA650E2B04E03E9A407@onstor-exch02.onstor.net>
From: "Eric Barrett" <eric.barrett@onstor.com>
To: "Chris Vandever" <chris.vandever@onstor.com>,
	"dl-Customer-Engineering" <dl-Customer-Engineering@onstor.com>,
	"dl-Design Review" <dl-designreview@onstor.com>
Cc: "Charissa Willard" <charissa.willard@onstor.com>,
	"Brian DeForest" <brian.deforest@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C81BF2.C3FDCBBE
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Well, I filed at least one of those :)  My $0.02 is the bugs stand as
is.  Hostnames should not be case-sensitive, especially since virtual
servers (which one could think of as "sub-hosts") are not.

I don't know of any customer who currently expects hostnames to be case
sensitive, but doesn't mean there isn't one.


> _____________________________________________=20
> From: 	Chris Vandever =20
> Sent:	Wednesday, October 31, 2007 11:52 AM
> To:	dl-Customer-Engineering; dl-Design Review
> Cc:	Charissa Willard; Brian DeForest
> Subject:	Hostnames, Filer Names, and Cluster Names... Case
> Sensitive or Not?
>=20
> We have two ECRs we'd like to get some feedback on:
>=20
> *	#17831 (Gateway names should be case-insensitive)
> *	#11325 ("vsvr move -f filername" is case sensitive, "vsvr set
> vsvrname" is not)
>=20
> Currently, filer names and cluster names are case sensitive, just like
> the underlying hostname on which they are based in BSD.  Vsvr names
> and CIFS share names are case insensitive, and are converted to upper
> case before they are stored in the cluster database.
>=20
> Convenience would dictate that filer names and cluster names be case
> insensitive.  However, that imposes restrictions that do not exist for
> the underlying hostnames in BSD.  Do we have customers who rely on the
> names being case sensitive?  What do customers expect?
>=20
> Thoughts?
>=20
> ChrisV & Charissa
>=20

------_=_NextPart_001_01C81BF2.C3FDCBBE
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>RE: Hostnames, Filer Names, and Cluster Names... Case Sensitive =
or Not?</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=3D2 FACE=3D"Arial">Well, I filed at least one of those =
:)&nbsp; My $0.02 is the bugs stand as is.&nbsp; Hostnames should not be =
case-sensitive, especially since virtual servers (which one could think =
of as &quot;sub-hosts&quot;) are not.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I don't know of any customer who =
currently expects hostnames to be case sensitive, but doesn't mean there =
isn't one.</FONT>
</P>
<BR>

<P><FONT SIZE=3D1 =
FACE=3D"Tahoma">_____________________________________________ </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">From: &nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Chris Vandever&nbsp; </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">Sent:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Wednesday, October 31, 2007 11:52 AM</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Tahoma">dl-Customer-Engineering; dl-Design Review</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Cc:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Tahoma">Charissa Willard; Brian DeForest</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT>=
</B> <FONT SIZE=3D1 FACE=3D"Tahoma">Hostnames, Filer Names, and Cluster =
Names... Case Sensitive or Not?</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">We have two ECRs we&#8217;d like to get =
some feedback on:</FONT>
</P>
<UL>
<UL>
<LI><FONT SIZE=3D2 FACE=3D"Arial">#17831 (Gateway names should be =
case-insensitive)</FONT></LI>

<LI><FONT SIZE=3D2 FACE=3D"Arial">#11325 (&#8220;vsvr move -f =
filername&#8221; is case sensitive, &#8220;vsvr set vsvrname&#8221; is =
not)</FONT></LI>
<BR>
</UL></UL>
<P><FONT SIZE=3D2 FACE=3D"Arial">Currently, filer names and cluster =
names are case sensitive, just like the underlying hostname on which =
they are based in BSD.&nbsp; Vsvr names and CIFS share names are case =
insensitive, and are converted to upper case before they are stored in =
the cluster database.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Convenience would dictate that filer =
names and cluster names be case insensitive.&nbsp; However, that imposes =
restrictions that do not exist for the underlying hostnames in =
BSD.&nbsp; Do we have customers who rely on the names being case =
sensitive?&nbsp; What do customers expect?</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Thoughts?</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">ChrisV &amp; Charissa</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C81BF2.C3FDCBBE--
